This sounds like a good idea.

+1 this would be really helpful. I've wasted a lot of time trying to architect a productionised deployment of proton-bridge for my own use but struggle to make it play nice with the surrounding tooling. This would help a lot with that.

While not a solution for turning off STARTTLS, I've got a write-up about how to get Let's Encrypt certificates working with proton-bridge so you have valid TLS certificates

https://lder.dev/posts/Fixing-ProtonMail-Bridge-SSL-errors-with-Lets-Encrypt/

@jamolnng BTW, most smtp applications connecting with the bridge would work with starttls: disabled option. ( Tested with Nextcloud as well )

@ayanamidev Ya I did realize that for Nextcloud after I finished getting the certificates working, but I figured there might be one point where disabling starttls doesn't work for some application and I didn't want to be stuck

Also even though it should be only on the local network, the extra bit of security using TLS certificates, self-signed or not, gives that extra bit of comfort

I haven't tested but there does seem to be a way to change from STARTTLS to SSL, which would solve my use case issues.

Womp, appears the setting has no effect. Still runs in STARTTLS mode.

Appears this was added in v3. Can't wait!

indeed. feel free to test and let us know if doesn't work.

I can't get SSL to work with thunderbird.
I get an ssl_error_protocol_version_alert in the thunderbird console.